fix(react-router): preserve sourcemaps.disable override#20042
fix(react-router): preserve sourcemaps.disable override#20042
Conversation
Ensure unstable vite plugin options don't overwrite sourcemaps.disable=true and update test expectations accordingly. Co-Authored-By: gpt-5.3-codex-high <noreply@anthropic.com>
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Deps
Nuxt
Other
Bug Fixes 🐛Ci
Node
React Router
Other
Documentation 📚
Internal Changes 🔧Core
Deps
Deps Dev
Other
🤖 This preview updates automatically when you update the PR. |
5d78fc8 to
838a8e7
Compare
Ensure unstable vite plugin options don't overwrite sourcemaps.disable=true and update test expectations accordingly. Co-Authored-By: gpt-5.3-codex-high <noreply@anthropic.com>
838a8e7 to
a4d7eb2
Compare
size-limit report 📦
|
Ensure unstable vite plugin options don't overwrite sourcemaps.disable=true and update test expectations accordingly. Co-Authored-By: gpt-5.3-codex-high <noreply@anthropic.com>
a4d7eb2 to
ce47a95
Compare
Ensure unstable vite plugin options don't overwrite sourcemaps.disable=true and update test expectations accordingly. Co-Authored-By: gpt-5.3-codex-high <noreply@anthropic.com>
ce47a95 to
caedbb6
Compare
Ensure unstable vite plugin options don't overwrite sourcemaps.disable=true and update test expectations accordingly. Co-Authored-By: gpt-5.3-codex-high <noreply@anthropic.com>
caedbb6 to
1d54dd8
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| ...unstable_sentryVitePluginOptions?._metaOptions, | ||
| }, | ||
| reactComponentAnnotation: { | ||
| ...unstable_sentryVitePluginOptions?.reactComponentAnnotation, |
There was a problem hiding this comment.
Unstable reactComponentAnnotation values always overridden by undefined
Low Severity
The reactComponentAnnotation section spreads unstable_sentryVitePluginOptions?.reactComponentAnnotation first, but then enabled: reactComponentAnnotation?.enabled ?? undefined explicitly sets enabled to undefined when the user doesn't provide it, overriding any unstable fallback value. The ?? undefined is a no-op. This is inconsistent with the release pattern, which uses ...release and naturally preserves unstable values when the main option isn't provided. Using ...reactComponentAnnotation instead of the explicit property assignments would be consistent.


Ensure unstable vite plugin options don't overwrite sourcemaps.disable=true and update test expectations accordingly.
Before submitting a pull request, please take a look at our
Small issue found by cursor in #19890 right before it got merged.